Alert Notification System and Message Overviews Document Version: 2.6 Date: November 11, 2021
Copyright © 2009-2023 Jeppesen. All rights reserved.
Your use of the AIM Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen.
The AIM Bookshelf is delivered "AS IS" without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AIM Bookshelf at your own risk. No support for the AIM Bookshelf is implied through its publication. The AIM Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AIM Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts.
Document Revision History The following revision history table reflects all substantive changes to this document.
Table Of Contents
1 IntroductionThis document defines the interfaces which govern the interchange of data between an Alert Notification system and other systems within an Airline Operation Center (AOC). Each AOC interface is represented by a message described in an associated XSD (XML Schema Definition). The XSD defines and enforces the required, optional, and conditional data that can be included in a message. 1.1 AudienceThe intended audience for this document includes existing and potential Jeppesen customers, integration partners, and personnel with roles associated with application architecture, application development, system testing, implementation, and application support for any programs that require the Alert Notification system. 1.2 ScopeThis document discusses the Alert Notification messages currently supported by the Jeppesen Solution Integrator. Each message description includes the following:
Other data interfaces or formats not included in this document will be considered custom and not supported. 1.3 XML Schema/XSDThe XML schema for this ICD is published in the following file: AlertNotification.XSD
2 Message SummaryTable 2-1 lists the messages that can be sent or handled by the application. The messages originated by this application (messages that begin with “AN”) are further discussed in Section 3 AOC Interface Messages.
3 AOC Interface MessagesThe following messages are processed by the Alert Notification system. 3.1 AN001 – Alert3.1.1 Message OverviewThis message sends an unsolicited message (i.e. alert) to systems within the AOC. The message includes a configurable alert level (1-4), which can be used to trigger custom behavior in the recipient system, and a text description of the alert. These alerts can be sent to flights or desks. 3.1.2 Message System FlowThis message interacts with the systems as shown in Figure 1. 3.1.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
3.2 AN002 – Error Notification3.2.1 Message OverviewThis message returns errors related to AOCi messages to the sending product. This message can include similar information that is currently captured in the AOCi server log. 3.2.2 Message System FlowThis message interacts with the systems as shown in Figure 2. 3.2.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
3.3 AN003 – NOTAM Alert3.3.1 Message OverviewThe AN003 message is sent from a NOTAM Management Tool to a downstream client system (i.e. Dispatch or Flight Planning system). The AN003 alerts the downstream client system of any new or cancelled NOTAM messages associated with a registered flight that has been flagged to send alerts. Figure 3 illustrates a sample use case for this message.
3.3.2 Message System FlowThis message interacts with the systems as shown in Figure 4. 3.3.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
3.4 AN004 – Desk Assignment Notification3.4.1 Message OverviewThe Message Overview for this version is not yet available for this DRAFT version. 3.4.2 Message System FlowThe Message System Flow diagram is not yet available for this DRAFT version. 3.4.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
3.5 AN005 – Desk Assignment Alert Query3.5.1 Message OverviewThe Message Overview for this version is not yet available for this DRAFT version. 3.5.2 Message System FlowThe Message System Flow diagram is not yet available for this DRAFT version. 3.5.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
|